Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Address ZDI-20-1051 / ZDI-CAN-10436: Prevent deserializing a class. #10

Merged
merged 1 commit into from
Oct 22, 2022

Conversation

ralflang
Copy link
Member

Deal with https://www.zerodayinitiative.com/advisories/ZDI-20-1051/

Also guard against some other possibly unwanted deserialisations. It is debatable if this constitutes an actual attack vector before the change. However, the change rules out any such possibility.
See discussion on the ML https://lists.horde.org/archives/horde/Week-of-Mon-20221010/059302.html

@mrubinsk I have given this some limited functional testing but it might make sense to have a closer look.

Also guard against some other possibly unwanted deserialisations.
It is debatable if this constitutes an actual attack vector before the change.
However, the change rules out any such possibility.
@ralflang
Copy link
Member Author

I think this is fit for master but not for FW_5_2 as-is due to used PHP features.

@mrubinsk
Copy link
Member

I agree. The allowed_classes option isn't available until PHP 7.0 so this can't be used in FW_5_2. Also note that this would only be a stop gap for this specific preference while we implement a more complete refactoring/replacing of how we handle allowing this prefs to be set.

@mrubinsk mrubinsk merged commit 5f9aef5 into horde:master Oct 22, 2022
@ralflang
Copy link
Member Author

I agree. I was working on a more general solution but it needs a little more time.

ralflang pushed a commit that referenced this pull request Dec 22, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
2 participants